Software Engineering Project 1 - 4010-561-14.20082 : Risk Management Table
This page last changed on Jan 21, 2009 by pwy4104.
ID Rank Risk Description Category Root Cause Triggers Potential Responses Owner Probability Impact (hours) Total
Status & Actions Taken to Reduce Likelihood
6
1
Testing Environment Testing tasks/use cases are impeded.
Environment Cannot feasibly test task/story or cannot develop adequate test case with available tools. 
  • User story is impeded for at most a day
  • See advice of other team members
  • Consult with sponsor/product owner
 Test Lead
.80
20
16 Investigating confluence integration test  framework (active)
13
2
Role Mapping Confluence users cannot be mapped to SQL users.
Session Related Issues SQL users cannot be mapped to Confluence users or are unknown.  Cannot connect to databases using users information acquired through Confluence
  • Discuss alternatives with Product Owner(s)
  • Is it required?
.85
15
12.75 - depends on if feature will be implemented
9
3
Database Support Issues
Stories/tasks related to certain row operations could be impeded.
SQL Specific Issues
  • Implementations of SQL that do not conform to standards
  • Advanced vendor specific feature
 Database test cases fail
  • Evaluate trade-offs
  • Discuss necessity of specific vendor support with Product Owner(s)
.95
12
11.4 - spiking potential issues
12 4
Technical Design Issues
Unsure how to manage server side results for future editing
Plugin development
Inexperience or lack of domain knowledge, complex problems 
Severe early impediment to database editing related tasks
  • Speak with sponsor
  • Consult with faculty advisor
  • Readjust sprint priorities
 TBA
.40
20
8
7
5
Javascript/JQuery
Javascript/JQuery development stories/tasks are impeded. AJAX Lack of skills/knowledge/experience with Javascript/JQuery
  • Lack of progress for user story/task
  • Seek advice of team members
  • Re-evaluate use of Javascript for task/story with Product Owner(s)
 TBA
.60
4
2.4
2 6
Confluence Wiki Team is unable to complete user stories due to technical challenges with Confluence Plugin architecture/ APIs.
Plugin Development Development team has no previous experience working with Confluence Wiki. User story/task is marked as having a confluence API related impediment for more than 3 days
  • Move story to back-burner
  • Move to future sprint
  • Discuss user story with Product Owner(s)
 TBA
.25
8
2
8 7
Communication Possible miscommunications between the development team and stakeholders. Stakeholders Geographical separation, misunderstanding of subject matter/domain/technologies
At iteration planning meetings, review meetings, there are unmet expectations.
  • Compromise with product owner
  • Add stories to address unmet needs
  • Change communication methods
 TBA
.2
6
1.2
10 8
Integration Since the project must integrate properly with the already existing SQL plugin, design/implementation choices. Open Source Community
SQL plugin design
Design/implementation of features impeded by existing SQL plugin design.
  • Investigate work-a-rounds
  • Communicate with Bob Swift
  • Develop plug-in as a standalone
  • Adapt existing plug-in to ours (re-direct old-style requests?)
 Scrum Master/ Product Owner
.5
2
1
4
9
Flow of Events User stories related to AJAX/client-server interactions may not be completed or are impeded.
Plugin Development Lack of knowledge on how Confluence handles requests. TBD / Unknown?
  • Re-prioritize story
  • Consult with product owner(s)
  • Do more technology prototyping/spiking/research
 TBA
.15
4
.6
- after initial technology spike team is more comfortable with plugin flow of events
5
10
Virtual Machine Virtual Machine is unavailable for development.
Environment
  • Crash
  • Bad configuration
 VM is unavailable for 10 minutes.
  • Work with Kurt to resolve issue
  • Designate a team member's computer as the temporary test environment if necessary
 Configuration Lead
.20
2
.4
14
10 Poor estimation Estimations are too low and leads to readjusting priorities and sprint backlog.
Scrum methodology
Inexperience Consistently high estimation error %, sprint goals not being met
  • Planning resolution meeting
  • Try new estimation techniques
 Sprint scrum master .2 2 (does not include non-quantifiable impacts)
.4 Estimation errors and scrum teams progress towards sprint goal will be tracked by Scrum Master throughout sprints
3
11
Compatibility
Interoperability with other Confluence Wiki plugins. Plugin Development Plugin cannot be used as a compatible macro for charting plugin (or other).
Charting fails to work when using the SQL macro.
  • Check test cases for failure
  • Fix code for outputting to wiki markup
 TBA
.10
2
.2
11 12
Plugin Ownership SQL Plugin owner(s) may not accept our work and integrate it with their plug-in
Bob Swift SQL Plugin owners are not responsive to e-mails, provide negative feedback regarding project.
Unknown (may happen after project is completed)
  • Release plugin separately
  • Xerox takes ownership of plugin
 Scrum master
.90
0? No impact on schedule, but would impact overall project success.
  Scrum master will contact Bob Swift (see other risk too).
1 6
Cannot build project (Maven) The project cannot be built using Maven.  Plugin Development Development team has no previous experience working with Maven. Cannot build due to configuration problems
  • consult expert
 Eugene
 0
5
0
 Mitigated

Attachments:
worddav6d66c7298544d949fa8915dd2e170469.png (image/png)
Document generated by Confluence on May 21, 2009 10:23